Vesan Terakol
Sad Face Enterprises
20
   |
Posted - 2013.11.13 14:21:00 -
[1] - Quote
I would like to further iterate on the aforementioned module, that would provide intel on system entry in place of local.
Make it so such a module needs to "lock" its target in order to provide detailed intel. E.G:
1 - A cruiser jumps in and aligns away - the structure "locks" the cruiser and genrates a mesage: "X has entered the system XM-PL1 at hh:mm." There is also a link, that contains all the scanned ships in a window, similar than those, generate by survey scanner - ship class, ship name.
2 - X jumps again in the sysem, but has 6 buddies with him - Y, Z, J,H,K. The basic scanner you've placed has a maximum of 5 locked targets at once, so it will generate the message: "X,Y,Z,J,H and one more have entered the system XM-PL1" If K sticks around the gate for a given period (lets say 15 secs), the module will initiate a new scan and add K to the list"
3 - 2 minutes before X, the scout A and scout in training B have passed through the same gate, both in covops ships. A is quick on the cloak and engages it before the structure manages to pick him up. B gets distracted, so the scanner detects his presence, but doesn't manage to get a lock. The message reads "1 unknown ship has entered the system XM-PL1"
Now, those examples cover a few more advanced concepts - basic detection, rescan timers and intel update and covops ship grace period before scanning.
Basic detection occurs when the station initiates a lock attempt on the target. If the lock fails, the ship will be listed as unknown.
Rescan and update will trigger at a set amount of time (lets use 15 secs as example). Instead of classical lock system, where a new target can be locked as soon as one dissapears, the target logic allocates a a set amount of time (15 secs) to each locked target. The "slot" remains closed for 15 secs, regardless of whether lock is maintained or not. If a new ship gets locked within a minute of the generated report, it will be added to the already existing list, keeping the generated intel less messy.
Covops ships, being sneaky, get a limited grace period, allowing for the swap between gate cloak and their own cloak, during which a lock attempt will not commence. its worth noticing, that a lock attempt can commence while a target is untargetable - jumping away - and it will generate an "unknown" entry.
Now, after all this message stuff, you would wonder, where all that data will be dumped - when the structure is activated, the owner is prompted to input a chat name - the structure would dump all intel generated in the chat, to which it is attached. |